Closed
Conversation
* Created May folder. Updated version for exampls, commands * Updated package to May version * Returned NW examples * Fixed API version; Fixed NetworkWatcher examples * Fixed VPN Gateway/Connection examples * Add changes from PR#2975 https://github.com/Azure/azure-rest-api-specs/pull/2975/files
…nfig object for enhancing the Network Watcher cmdlets (Azure#3023) * Adding optional traffic analytics parameters with existing network watched flowlog configuration * Updating the version * Updating latest versoin in readme.md
* Adding optional traffic analytics parameters with existing network watched flowlog configuration * Updating the version * Updating latest versoin in readme.md * Adding optional traffic analytics parameters with flowlog parameters * Reverting old chnages
Expose new SKUs for VMSS VPN and ER gateways
* Initial network error fixes and suppressions * reworked exception to specified code blocks only * Added express route fixes
vinayada1
requested review from
DeepakRajendranMsft and
MikhailTryakhov
as code owners
Automation for azure-libraries-for-javaEncountered a Subprocess error: (azure-libraries-for-java)
Command: ['/usr/local/bin/autorest', '/tmp/tmp_u57iwo2/rest/specification/network/resource-manager/readme.md', '--azure-libraries-for-java-folder=/tmp/tmp_u57iwo2/sdk', '--fluent', '--java', '--multiapi', '--verbose'] AutoRest code generation utility [version: 2.0.4262; node: v7.10.1]
(C) 2018 Microsoft Corporation.
https://aka.ms/autorest
Loading AutoRest core '/root/.autorest/@microsoft.azure_autorest-core@2.0.4278/node_modules/@microsoft.azure/autorest-core/dist' (2.0.4278)
Loading AutoRest extension '@microsoft.azure/autorest.java' (~2.1.32->2.1.70)
Loading AutoRest extension '@microsoft.azure/autorest.modeler' (2.3.38->2.3.38)
ERROR: Syntax Error Encountered: Unexpected token , in JSON
- file:///tmp/tmp_u57iwo2/rest/specification/network/resource-manager/Microsoft.Network/stable/2018-05-01/expressRouteCircuit.json:1207:3
ERROR: Syntax error: end of the stream or a document separator is expected
- file:///tmp/tmp_u57iwo2/rest/specification/network/resource-manager/Microsoft.Network/stable/2018-05-01/expressRouteCircuit.json:1207:3
ERROR: Syntax error: end of the stream or a document separator is expected
- file:///tmp/tmp_u57iwo2/rest/specification/network/resource-manager/Microsoft.Network/stable/2018-05-01/expressRouteCircuit.json:1928:3
ERROR: Syntax error: end of the stream or a document separator is expected
- file:///tmp/tmp_u57iwo2/rest/specification/network/resource-manager/Microsoft.Network/stable/2018-05-01/expressRouteCircuit.json:1945:0
ERROR: Syntax error: expected a single document in the stream, but found more
- file:///tmp/tmp_u57iwo2/rest/specification/network/resource-manager/Microsoft.Network/stable/2018-05-01/expressRouteCircuit.json:1207:3
FATAL: swagger-document/loader - FAILED
FATAL: Error: Syntax errors encountered.
Process() cancelled due to exception : Syntax errors encountered.
Error: Syntax errors encountered. |
Automation for azure-sdk-for-nodeNothing to generate for azure-sdk-for-node |
Automation for azure-sdk-for-pythonA PR has been created for you based on this PR content. Once this PR will be merged, content will be added to your service PR: |
Automation for azure-sdk-for-goEncountered a Subprocess error: (azure-sdk-for-go)
Command: ['/usr/local/bin/autorest', '/tmp/tmp3xhistop/rest/specification/network/resource-manager/readme.md', '--go', '--go-sdk-folder=/tmp/tmp3xhistop/src/github.com/Azure/azure-sdk-for-go', '--multiapi', '--use=@microsoft.azure/autorest.go@~2.1.105', '--use-onever', '--verbose'] AutoRest code generation utility [version: 2.0.4280; node: v7.10.1]
(C) 2018 Microsoft Corporation.
https://aka.ms/autorest
Loading AutoRest core '/root/.autorest/@microsoft.azure_autorest-core@2.0.4280/node_modules/@microsoft.azure/autorest-core/dist' (2.0.4280)
Loading AutoRest extension '@microsoft.azure/autorest.go' (~2.1.105->2.1.105)
Loading AutoRest extension '@microsoft.azure/autorest.modeler' (2.3.38->2.3.38)
Processing batch task - {"tag":"package-2018-05"} .
ERROR: Syntax Error Encountered: Unexpected token , in JSON
- file:///tmp/tmp3xhistop/rest/specification/network/resource-manager/Microsoft.Network/stable/2018-05-01/expressRouteCircuit.json:1207:3
ERROR: Syntax error: end of the stream or a document separator is expected
- file:///tmp/tmp3xhistop/rest/specification/network/resource-manager/Microsoft.Network/stable/2018-05-01/expressRouteCircuit.json:1207:3
ERROR: Syntax error: end of the stream or a document separator is expected
- file:///tmp/tmp3xhistop/rest/specification/network/resource-manager/Microsoft.Network/stable/2018-05-01/expressRouteCircuit.json:1928:3
ERROR: Syntax error: end of the stream or a document separator is expected
- file:///tmp/tmp3xhistop/rest/specification/network/resource-manager/Microsoft.Network/stable/2018-05-01/expressRouteCircuit.json:1945:0
ERROR: Syntax error: expected a single document in the stream, but found more
- file:///tmp/tmp3xhistop/rest/specification/network/resource-manager/Microsoft.Network/stable/2018-05-01/expressRouteCircuit.json:1207:3
FATAL: swagger-document/loader - FAILED
FATAL: Error: Syntax errors encountered.
Process() cancelled due to exception : Syntax errors encountered.
Failure during batch task - {"tag":"package-2018-05"} -- Error: Syntax errors encountered..
Error: Syntax errors encountered. |
jianghaolu
reviewed
May 18, 2018
| @@ -0,0 +1 @@ | |||
| { "parameters": { "expressRouteCircuitName": "circuitName", "resourceGroupName": "rg1", "api-version": "2017-11-01", "subscriptionId": "subid", "peeringName": "peeringName", "devicePath": "devicePath" }, "responses": { "200": { "value": [ { "age": 0, "interface": "Microsoft", "ipAddress": "IPAddress", "macAddress": "macAddress" } ] }, "202": { "value": [ { "age": 0, "interface": "Microsoft", "ipAddress": "IPAddress", "macAddress": "macAddress" } ] } } } | |||
Contributor
There was a problem hiding this comment.
Please configure your git to check in Unix style line endings.
Automation for azure-sdk-for-rubyNothing to generate for azure-sdk-for-ruby |
MikhailTryakhov
suggested changes
May 28, 2018
Contributor
MikhailTryakhov
left a comment
MikhailTryakhov
left a comment
There was a problem hiding this comment.
Please follow comments in the PR
Contributor
|
@gimotwanMSFT please push your PR to Network-2018-06-01 branch, merge your changes with master. |
Contributor
|
@gimotwanMSFT please make your changes in |
Automation for azure-sdk-for-javaEncountered a Subprocess error: (azure-sdk-for-java)
Command: ['/usr/local/bin/autorest', '/tmp/tmpy04otfnh/rest/specification/network/resource-manager/readme.md', '--azure-libraries-for-java-folder=/tmp/tmpy04otfnh/sdk', '--java', '--multiapi', '--use=@microsoft.azure/autorest.java@2.1.71', '--verbose'] AutoRest code generation utility [version: 2.0.4280; node: v7.10.1]
(C) 2018 Microsoft Corporation.
https://aka.ms/autorest
Loading AutoRest core '/root/.autorest/@microsoft.azure_autorest-core@2.0.4280/node_modules/@microsoft.azure/autorest-core/dist' (2.0.4280)
Loading AutoRest extension '@microsoft.azure/autorest.java' (2.1.71->2.1.71)
Loading AutoRest extension '@microsoft.azure/autorest.modeler' (2.3.38->2.3.38)
Processing batch task - {"tag":"package-2018-05"} .
ERROR: Syntax Error Encountered: Unexpected token , in JSON
- file:///tmp/tmpy04otfnh/rest/specification/network/resource-manager/Microsoft.Network/stable/2018-05-01/expressRouteCircuit.json:1207:3
ERROR: Syntax error: end of the stream or a document separator is expected
- file:///tmp/tmpy04otfnh/rest/specification/network/resource-manager/Microsoft.Network/stable/2018-05-01/expressRouteCircuit.json:1207:3
ERROR: Syntax error: end of the stream or a document separator is expected
- file:///tmp/tmpy04otfnh/rest/specification/network/resource-manager/Microsoft.Network/stable/2018-05-01/expressRouteCircuit.json:1928:3
ERROR: Syntax error: end of the stream or a document separator is expected
- file:///tmp/tmpy04otfnh/rest/specification/network/resource-manager/Microsoft.Network/stable/2018-05-01/expressRouteCircuit.json:1945:0
ERROR: Syntax error: expected a single document in the stream, but found more
- file:///tmp/tmpy04otfnh/rest/specification/network/resource-manager/Microsoft.Network/stable/2018-05-01/expressRouteCircuit.json:1207:3
FATAL: swagger-document/loader - FAILED
FATAL: Error: Syntax errors encountered.
Process() cancelled due to exception : Syntax errors encountered.
Failure during batch task - {"tag":"package-2018-05"} -- Error: Syntax errors encountered..
Error: Syntax errors encountered. |
mccleanp
pushed a commit
that referenced
this pull request
Mar 23, 2022
Removing header details in the swagger
konrad-jamrozik
pushed a commit
to dhung-msft/azure-rest-api-specs
that referenced
this pull request
Dec 4, 2023
…tch-7 [Internal testing] testing openapi-alps PR 510778 - Test 11/15/2023 / 1
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
9 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information
api-versionin the path should match theapi-versionin the spec).Quality of Swagger